Method and System for Automatic Detection, Inventory, and Operating System Deployment on Network Boot Capable Computers

ABSTRACT

A system for the automatic detection and inventory of a network boot capable computer and for the automatic deployment of an appropriate operating system to the network boot capable computer. First, an initial broadcast packet from the network boot capable computer is received. In response to receiving the initial broadcast packet, a discovery kernel is sent to the network boot capable computer. The discovery kernel generates a hardware details file. The hardware details file is received from the network boot capable computer and is analyzed. After the hardware details file is analyzed, an appropriate operating system is deployed to the network boot capable computer.

BACKGROUND OF THE INVENTION

1. Technical Field

The present invention relates to an improved data processing system.More specifically, the present invention is directed to a method,apparatus, and computer program product for the detection, inventory,and installation of an operating system on network boot capablecomputers.

2. Description of Related Art

A desktop management interface is a management system for personalcomputers developed by the Distributed Management Task Force. Thedesktop management interface, or DMI, provides a bi-directional path tointerrogate all the hardware and software components within a computer.When computers are DMI-enabled, the hardware and software configurationsof the computers may be monitored over a network from a central station.

A computer utilizing DMI technology has a memory-resident agent residingin the background of the operating system. When the DMI queries theagent, the agent will respond by sending back data contained in amanagement information file and/or activating a management informationfile routine. The management information file may contain static data,such as, computer model identification, serial number, memory and portaddresses. A management information file routine may, for example,report errors to a management console as errors occur, or the managementinformation file routine may scan read-only-memory orrandom-access-memory chips and report their contents, as well.

Wired for management (WfM) is a specification from the Intel™Corporation for a computer that can be centrally managed in a network.The computer must be DMI compliant, be accessible by a management serverprior to booting, contain instrumentation for component discovery andidentification and include remote wake-up capabilities. A prebootexecution environment (PXE) is an Intel™ WfM capability that enables acomputer to boot from a server. PXE enables remote booting of anoperating system; remote emergency booting of a diagnostic program; andremote new system startup, which will boot an installation program toinstall an operating system. PXE is supported in the basic input outputsystem (BIOS). BIOS is an essential set of routines in a computer, whichare stored on a chip and provides an interface between the operatingsystem and the hardware. The operating system (OS) is the master controlprogram that runs a data processing system. The OS starts andcommunicates with all software programs that run in the data processingsystem.

A dynamic host configuration protocol (DHCP) is a software program thatautomatically assigns internet protocol (IP) addresses to clientstations logging onto a transmission control protocol/internet protocol(TCP/IP) network. An IP address is the address of a computer attached toan IP network. Every client and server station must have a unique IPaddress. A trivial file transfer protocol (TFTP) is a version of theTCP/IP file transfer protocol that has no directory or passwordcapability.

For clarification, a client is a requesting machine and a server is asupplying machine, both of which are connected via a network. A clienthas either a permanent IP address or one that is dynamically assigned toa client when booted. DHCP eliminates having to manually assignpermanent IP addresses to a client. DHCP software typically runs inservers and is also found in network devices, such as, integratedservices digital network (ISDN) routers and modem routers that allow amultitude of users access to the Internet.

A bootstrap protocol (BOOTP) is a TCP/IP protocol used by a disklessworkstation or network computer to obtain its IP address and othernetwork information such as server address and default gateway. Uponstartup, a client sends out a BOOTP request in a user datagram protocol(UDP) packet to the BOOTP server, which returns the requiredinformation.

A problem with existing remote inventory and deployment systems, suchas, for example, Rembo™ Auto-Deploy Technology, International BusinessMachines™ Corporation's Remote Deployment Manager, or Microsoft™ WindowServer 2003 Automated Deployment Services, is that the above listedsystems are limited to supporting only one type of computer hardware oroperating system. Another problem with current client/server managementsystems is that all information with regard to a client machine has tobe input into a database manually by the system administrator using agraphical user interface (GUI) or by importing a file containing therequired information.

Therefore, it would be advantageous to have an improved method andapparatus for the detection, inventory, and deployment of an operatingsystem to network boot capable computers.

SUMMARY OF THE INVENTION

Embodiments of the present invention provide a method, apparatus and acomputer program product for automatically detecting and inventorying anetwork boot capable computer. Further, the present invention provides amethod, apparatus and a computer program product for automaticallydeploying an appropriate operating system to the network boot capablecomputer.

The process starts when an initial broadcast packet from the networkboot capable computer is received. In response to receiving the initialbroadcast packet, a discovery kernel is sent to the network boot capablecomputer. The discovery kernel is loaded by the network boot capablecomputer and generates a hardware details file. The hardware detailsfile is received from the network boot capable computer and is analyzed.Subsequent to the analysis of the hardware details file, an appropriateoperating system is deployed to the network boot capable computer.

BRIEF DESCRIPTION OF THE DRAWINGS

The novel features believed characteristic of embodiments of theinvention are set forth in the appended claims. The embodiments of theinvention, as well as a preferred mode of use, further objectives andadvantages thereof, will best be understood by reference to thefollowing detailed description of an illustrative embodiment when readin conjunction with the accompanying drawings, wherein:

FIG. 1 is a pictorial representation of a distributed data processingsystem in which embodiments of the present invention may be implemented;

FIG. 2 is an exemplary block diagram of a data processing system thatmay be implemented as a server, such as a server in FIG. 1, inaccordance with an embodiment of the present invention;

FIG. 3 is a block diagram illustrating a data processing system that maybe implemented as a client, such as a client in FIG. 1, in accordancewith an embodiment of the present invention;

FIG. 4 is an exemplary block diagram which illustrates the exchange ofinformation and software programs between a client and a boot server inaccordance with an embodiment of the present invention;

FIG. 5 is an exemplary pictorial illustration of the informationcontained in a client hardware details file in accordance with anembodiment of the present invention;

FIG. 6 is a flowchart illustrating an exemplary process for receiving anoperating system from a boot server in accordance with an embodiment ofthe present invention; and

FIG. 7 is a flowchart illustrating an exemplary process for deploying anoperating system from a boot server to a client in accordance with anembodiment of the present invention.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT

With reference now to the figures, FIG. 1 depicts a pictorialrepresentation of a distributed data processing system in whichembodiments of the present invention may be implemented. Distributeddata processing system 100 is a network of computers in which anembodiment of the present invention may be implemented. Distributed dataprocessing system 100 contains a network 102, which is the medium usedto provide communications links between various devices and computersconnected together within distributed data processing system 100.Network 102 may include permanent connections, such as wire or fiberoptic cables, or temporary connections made through telephoneconnections.

In the depicted example, a server 104 is connected to network 102 alongwith storage unit 106. In addition, clients 108, 110, and 112 also areconnected to network 102. These clients 108, 110, and 112 may be, forexample, personal computers or network computers. For purposes of thisapplication, a network computer is any computer, coupled to a network,which receives a program or other application from another computercoupled to the network. In the depicted example, server 104 providesdata, such as boot files, operating system images, and applications toclients 108-112. Clients 108, 110, and 112 are clients to server 104.Distributed data processing system 100 may include additional servers,clients, and other devices not shown. In the depicted example,distributed data processing system 100 is the Internet with network 102representing a worldwide collection of networks and gateways that usethe TCP/IP suite of protocols to communicate with one another. At theheart of the Internet is a backbone of high-speed data communicationlines between major nodes or host computers, consisting of thousands ofcommercial, government, educational and other computer systems thatroute data and messages. Of course, distributed data processing system100 also may be implemented as a number of different types of networks,such as for example, an intranet, a local area network (LAN), or a widearea network (WAN). FIG. 1 is intended as an example, and not as anarchitectural limitation for embodiments of the present invention.

Referring to FIG. 2, a block diagram of a data processing system thatmay be implemented as a server, such as server 104 in FIG. 1, isdepicted in accordance with an embodiment of the present invention. Dataprocessing system 200 may be a symmetric multiprocessor (SMP) systemincluding a plurality of processors 202 and 204 connected to system bus206. Alternatively, a single processor system may be employed. Alsoconnected to system bus 206 is memory controller/cache 208, whichprovides an interface to local memory 209. I/O bus bridge 210 isconnected to system bus 206 and provides an interface to I/O bus 212.Memory controller/cache 208 and I/O bus bridge 210 may be integrated asdepicted.

Peripheral component interconnect (PCI) bus bridge 214 connected to I/Obus 212 provides an interface to PCI local bus 216. A number of modemsmay be connected to PCI bus 216. Typical PCI bus implementations willsupport four PCI expansion slots or add-in connectors. Communicationslinks to network computers 108-112 in FIG. 1 may be provided throughmodem 218 and network adapter 220 connected to PCI local bus 216 throughadd-in boards.

Additional PCI bus bridges 222 and 224 provide interfaces for additionalPCI buses 226 and 228, from which additional modems or network adaptersmay be supported. In this manner, data processing system 200 allowsconnections to multiple network computers. A memory-mapped graphicsadapter 230 and hard disk 232 may also be connected to I/O bus 212 asdepicted, either directly or indirectly.

Those of ordinary skill in the art will appreciate that the hardwaredepicted in FIG. 2 may vary. For example, other peripheral devices, suchas optical disk drives and the like, also may be used in addition to orin place of the hardware depicted. The depicted example is not meant toimply architectural limitations with respect to an embodiment of thepresent invention.

The data processing system depicted in FIG. 2 may be, for example, anIBM™ eServer pSeries system, a product of International BusinessMachines™ Corporation in Armonk, N.Y., running the Advanced InteractiveExecutive (AIX™) operating system or the LINUX™ operating system.

With reference now to FIG. 3, a block diagram illustrating a dataprocessing system in which an embodiment of the present invention may beimplemented. Data processing system 300 is an example of a clientcomputer. Data processing system 300 employs a peripheral componentinterconnect (PCI) local bus architecture. Although the depicted exampleemploys a PCI bus, other bus architectures such as Accelerated GraphicsPort (AGP) and Industry Standard Architecture (ISA) may be used.Processor 302 and main memory 304 are connected to PCI local bus 306through PCI bridge 308. PCI bridge 308 also may include an integratedmemory controller and cache memory for processor 302. Additionalconnections to PCI local bus 306 may be made through direct componentinterconnection or through add-in boards. In the depicted example, localarea network (LAN) adapter 310, SCSI host bus adapter 312, and expansionbus interface 314 are connected to PCI local bus 306 by direct componentconnection. In contrast, audio adapter 316, graphics adapter 318, andaudio/video adapter 319 are connected to PCI local bus 306 by add-inboards inserted into expansion slots. Expansion bus interface 314provides a connection for a keyboard and mouse adapter 320, modem 322,and additional memory 324. Small computer system interface (SCSI) hostbus adapter 312 provides a connection for hard disk drive 326, tapedrive 328, and CD-ROM drive 330. Typical PCI local bus implementationswill support three or four PCI expansion slots or add-in connectors.

An operating system runs on processor 302 and is used to coordinate andprovide control of various components within data processing system 300in FIG. 3. The operating system may be a commercially availableoperating system, such as Windows™ 2000, which is available fromMicrosoft™ Corporation. An object oriented programming system such asJava™ may run in conjunction with the operating system and providescalls to the operating system from Java™ programs or applicationsexecuting on data processing system 300. “Java” is a trademark of SunMicrosystems™, Inc. Instructions for the operating system, theobject-oriented operating system, and applications or programs arelocated on storage devices, such as hard disk drive 326, and may beloaded into main memory 304 for execution by processor 302.

Those of ordinary skill in the art will appreciate that the hardware inFIG. 3 may vary depending on the implementation. Other internal hardwareor peripheral devices, such as flash ROM (or equivalent nonvolatilememory) or optical disk drives and the like, may be used in addition toor in place of the hardware depicted in FIG. 3. Also, the processes ofan embodiment of the present invention may be applied to amultiprocessor data processing system.

For example, data processing system 300, if optionally configured as anetwork computer, may not include SCSI host bus adapter 312, hard diskdrive 326, tape drive 328, and CD-ROM 330, as noted by dotted line 332in FIG. 3 denoting optional inclusion. In that case, the computer, to beproperly called a client computer, must include some type of networkcommunication interface, such as LAN adapter 310, modem 322, or thelike. As another example, data processing system 300 may be astand-alone system configured to be bootable without relying on sometype of network communication interface, whether or not data processingsystem 300 comprises some type of network communication interface. As afurther example, data processing system 300 may be a Personal DigitalAssistant (PDA) device, which is configured with ROM and/or flash ROM inorder to provide non-volatile memory for storing operating system filesand/or user-generated data.

The depicted example in FIG. 3 and above-described examples are notmeant to imply architectural limitations. For example, data processingsystem 300 also may be a notebook computer or hand held computer inaddition to taking the form of a PDA. Data processing system 300 alsomay be a kiosk or a Web appliance.

An embodiment of the present invention provides an improved method,apparatus, and computer implemented instructions for automatic detectionand inventory of a network boot capable computer. Moreover, anembodiment of the present invention provides a method, apparatus and acomputer program product for automatic deployment of an appropriateoperating system to the network boot capable computer. To begin theprocess, an initial broadcast packet is received from the network bootcapable computer. In response to receiving the initial broadcast packet,a discovery kernel is sent to the network boot capable computer. Thediscovery kernel is loaded by the network boot capable computer andgenerates a hardware details file of the network boot capable computer.The hardware details file is received from the network boot capablecomputer and is analyzed. After analyzing the hardware details fileusing a deployment policy, an appropriate operating system is selectedand deployed to the network boot capable computer.

A feature of an embodiment of the present invention is that anembodiment of the present invention will make it possible to identify,inventory, and manage different computer platforms and differentoperating systems for a plurality of clients remotely from one centralboot server. Examples of currently available computer hardware platformsproduced by different manufacturers are Intel™'s x86 PC, IBM™'s iSeries(AS/400), Advanced Micro Devices™' Opteron™, Hewlett-Packard™'s 9000series, and Sun Microsystem™'s SPARC™. Examples of currently availableoperating systems are IBM™ mainframe OS/390 and the AS/400's OS/400, themany versions of Windows™ (95, 98, NT, ME, 2000, and XP), versions ofUnix™ (Solaris™ and Linux™), Hewlett-Packard™ HP/UX OS, and theMacintosh™ OS. A problem with existing remote inventory and deploymentsystems is that they are limited to supporting only one type of computerhardware or operating system.

An embodiment of the present invention has the ability to deploymultiple, heterogeneous operating systems based on the physical locationof the client, even though all client systems have identical hardware.The client systems may be positioned in racks, shelves, etc., all havingthe same hardware. Information regarding the physical location of theclient may be used to deploy a plurality of operating systems to aplurality of clients. The physical location of the client may bepre-configured in the boot server of an embodiment of the presentinvention based on the client's serial number, globally uniqueidentifier (GUID), media access control (MAC) address, and the like. Theserial number may be found on a sticker on the computer case of theclient. Currently, commercial boot servers only have the ability todeploy one type of operating system to identical client hardwaresystems.

Another benefit of an embodiment of the present invention is that thesystem will drastically reduce the amount of time a datacenteradministrator will spend identifying, inventorying, and installingdiverse operating systems on a multitude of heterogeneous computers. Afurther feature of an embodiment of the present invention is that theidentification and inventory of network computers will be completelyautomatic and not require human intervention. Yet another benefit of anembodiment of the present invention is that the boot server can beimplemented on a commodity system with standard open source tools, suchas, for example, PXE and DHCP.

Referring now to FIG. 4, an exemplary block diagram which illustratesthe exchange of information and software programs between a client and aboot server in accordance with an embodiment of the present invention isshown. Network 400 is utilized to exchange the information and softwareprograms between boot server 410 and client 420, for example, whenserver 104 exchanges information and programs with clients 108, 110, and112 over network 102 in FIG. 1.

An embodiment of the present invention employs and utilizes thecapabilities of a preboot execution environment (PXE) and a dynamic hostconfiguration protocol/bootstrap protocol (DHCP/BootP) over network 400.PXE and DHCP/BootP are known protocols that enable a network computer toboot remotely from a server. For clarification, a boot server in thiscontext is a server that used to implement an embodiment of the presentinvention. A client is a network computer or any other system that iscapable of remote booting via a PXE environment or a DHCP/BootPenvironment. For example, an Intel™ computer is capable of remotebooting via PXE and an IBM™, Advanced Micro Devices™, Hewlett-Packard™,or Sun Microsystem™ computer is capable of remote booting viaDHCP/BootP. However, embodiments of the present invention are notrestricted to the immediately preceding list of data processing systemsor protocols. Any combination of compatible protocols and platformscapable of implementing the process of an embodiment of the presentinvention may be used.

It should be noted that an embodiment of the present invention mayaccommodate a plurality of clients powering on simultaneously. However,in the depicted example of FIG. 4, only one client is powered on. Atpower on, client 420 sends initial broadcast packet 440 over network 400to boot server 410. Client initial broadcast packet 440 may containinformation, such as, for example, manufacturer name or platform type.However, initial broadcast packet 440 may contain any basic informationnecessary for a boot server to utilize the system of an embodiment ofthe present invention.

In response to receiving client initial broadcast packet 440, bootserver 410 sends discovery kernel 450 to client 420. A kernel is afundamental part of a software program that typically is an operatingsystem. Based on the information contained in client initial broadcastpacket 440, boot server discovery kernel 450 will be an appropriatediscovery kernel for the system of client 420.

Client 420 will then load boot server discovery kernel from the trivialfile transfer protocol (TFTP) location specified in the response packet.Boot server discovery kernel 450, after being loaded by client 420,launches a hardware inventory scan of client 420. The inventory scanidentifies the hardware components of client 420, such as, for example,client serial number, manufacturer, platform type, central processingunit type and speed, network interface card type, and memory capability.

Subsequent to the inventory scan, boot server discovery kernel 450creates client hardware detail file 460. A specific example of thecontents of client hardware detail file 460 is provided in thedescription of FIG. 5 below. Client hardware detail file 460 is sent byclient 420 over a network file system (NFS), a file transfer protocol(FTP), or any other protocol capable of transferring client hardwaredetail file 460 to boot server 410 for analysis and storage. NFS is afile sharing protocol in a Unix™ network and FTP is a protocol that hasdirectory or password capability.

Storage of client hardware detail file 460 may be provided by inventorydatabase 430, such as, for example, local memory 209 in FIG. 2. However,client hardware detail file 460 may be stored in an inventory databaseof a different server or in a separate storage unit, such as, forexample, storage 106 in FIG. 1. Further, storage of client hardwaredetail file 460 may be provided by more than one storage unit in thesame or different locations or in any combination of the above. Stillfurther, client hardware detail file 460 may be sent to a managementsystem, such as, for example, the Tivoli™ Provisioning Manager, aproduct of International Business Machines™ Corporation in Armonk, N.Y.,for storage and file management.

Analysis of client hardware detail file 460 may be accomplished byprocessor 480, such as, for example, processor 202 or 204 in FIG. 2.Analysis of client hardware detail file 460 is for the purpose ofdetermining which operating system is to be deployed to client 420 fromboot server 410. For example, after analysis of client hardware detailfile 460 by processor 480, operating system 470 is deployed to client420 from boot server 410. Analysis of client hardware detail file 460 byprocessor 480 is based on boot server 410 deployment policies.

Boot server 410 deployment policies may be based on, for example, theserial number or processor type of client 420. As a specific example,boot server 410 deploys to client 420, with serial number 140nz2jX, aRedHat™ operating system or boot server 410 deploys to client 420, withan Intel™ processor, a Windows™ operating system. In addition,deployment policies may be related to the location of a client in a dataprocessing system. For example, a client in Rack-5, shelf-3 of dataprocessing system OMEGA is deployed a Solaris™ operating system, whereasa client in Rack-8, shelf-11 of data processing system OMEGA is deployeda Hewlett-Packard™ UX operating system. It should be noted that a bootserver utilizing the process of the present invention may have any kindor combination of deployment policies necessary to meet the requirementsof the clients that it supports.

When client 420 boots from network 400, instead of from a local harddisk, boot server 410 makes decisions based on the information receivedfrom client 420 and on the predefined deployment policies. For example,client initial broadcast packet 440 and client hardware detail file 460may indicate that client 420 is an Intel™ computer. Based on thatinformation, boot server 410 may deploy a RedHat™ Linux™ AS 3.0operating system customized for client 420.

Customization of the operating system specifically for client 420 mayinclude, for example, IP address allocation, routing configuration,usernames and passwords or any combination thereof. However, customizingan operating system for a specific client or groups of clients is notlimited to the immediately preceding list. A boot server employing thesystem of an embodiment of the present invention may customize theoperating system in any manner necessary to meet the needs of a client.

As another example, client initial broadcast packet 440 and clienthardware detail file 460 may indicate that client 420 is a SPARC™computer. Based on that information, boot server 410 may deploy aSolaris™ operating system customized for client 420. Also, boot server410 may group clients according to serial number, platform type, MACaddress, GUID, or any combination thereof. In addition, based onidentifying client groups, boot server 410 may automatically deploydifferent operating systems to the discrete groups of clients. It shouldbe noted that boot server 410 may deploy the same operating system or aplurality of operating systems to clients.

Subsequent to boot server 410 determining an appropriate operatingsystem for client 420, client 420 is rebooted and client initialbroadcast packet 440 is sent again over network 400. Boot server 410, inresponse to receiving client initial broadcast packet 440 once again,automatically deploys, over network 400, customized operating system470, which is to be installed on client 420. Operating system deploymentmay be performed by using specific technology, such as, for example,RedHat™ Kickstart, Solaris™ Jumpstart Automated Installation, andMicrosoft™ Automated Deployment Services, for the selected operatingsystem for the client. It should be noted that operating systemdeployment by the boot server may be to one or more clientssimultaneously.

Client 420 notifies boot server 410 after successful operating system470 deployment and installation. Boot server 410 may then notify amanagement system of the new status of client 420. If a managementsystem is used, the continued status of client 420 may be monitored bythe management system. Boot server 410 may continue to perform theinventory and deployment functions automatically.

Turning now to FIG. 5, an exemplary pictorial illustration of theinformation comprising a client hardware details file is depicted inaccordance with an embodiment of the present invention. Client hardwaredetail file 500, such as, for example, client hardware detail file 460in FIG. 4, may comprise the following information: client serial number,manufacturer of the system, platform type, MAC address, GUID, centralprocessing unit type and speed, network interface card, and hard disktype. However, it should be noted that client hardware detail file 500may contain more or less information depending upon the requirements ofa discovery kernel program sent to a client by a boot server utilizingthe system of the present invention. For example, boot server discoverykernel 450 sent to client 420 from boot server 410 in FIG. 4. Inaddition, all of the information contained on client hardware detailfile 500 may be associated with or identified by, for example, theclient serial number or any other item of information necessary toidentify the information with regard to that particular client hardwaredetail file.

With reference now to FIG. 6, a flowchart is shown illustrating anexemplary process for a client to receive an operating system from aboot server in accordance with an embodiment of the present invention.The process begins when a client powers on and sends an initialbroadcast packet over a network to a boot server (step 610). Forexample, client 420 powers on and sends client initial broadcast packet440 over network 400 to boot server 410 in FIG. 4.

The client will then launch a discovery kernel, such as, for example,boot server discovery kernel 450 in FIG. 4, sent to the client from theboot server in response to the boot server receiving the initialbroadcast packet (step 620). Subsequent to the client launching thediscovery kernel in step 620, the discovery kernel runs a hardwareinventory scan (step 630). After the hardware inventory scan isperformed by the discovery kernel in step 630, the client sends ahardware detail file (e.g., client hardware detail file 500 in FIG. 5)to the boot server over a network (step 640). For example, client 420sends client hardware detail file 460 to boot server 410 over network400 in FIG. 4.

Subsequent to the client hardware detail file being sent to the bootserver in step 640, the client reboots and sends an initial broadcastpacket to the boot server once again (step 650). In response toreceiving the initial broadcast packet once again from the client instep 650, the boot server deploys an appropriate operating system to theclient over the network. For example, boot server 410 deploys operatingsystem 470 over network 400 to client 420 in response to receivingclient initial broadcast packet 440 in FIG. 4 a second time. Finally,the client sends notification to the boot server that the deployment andinstallation of the operating system was successful (step 660). Theprocess terminates thereafter.

Referring now to FIG. 7, a flowchart illustrating an exemplary processfor deploying an operating system from a boot server to a client isdepicted in accordance with an embodiment of the present invention. Theprocess begins when a boot server sends a discovery kernel over anetwork to a client in response to receiving an initial broadcast packetfrom the client after client powers on (step 710). For example, bootserver 410 sends boot server discovery kernel 450 over network 400 toclient 420 in FIG. 4.

The discovery kernel runs a hardware scan of client. A client hardwaredetail file is generated by the discovery kernel and is sent by theclient to the boot server. Subsequently, the client hardware detail fileis stored in a database (step 720), such as, for example, clienthardware detail file 460 is stored in database 430 of boot server 410 inFIG. 4. In addition to storing the client hardware detail file in thedatabase in step 720, the information contained in the client hardwaredetail file, such as, for example, the information contained in clienthardware detail file 500 in FIG. 5, is analyzed according to apredetermined deployment policy. Boot server deployment policies arediscussed in the detailed description of FIG. 4 above. Analysis of theinformation contained in the client hardware detail file is performed bya processor in the boot server for the purpose of determining anappropriate operating system for deployment to the client (step 730).For example, processor 480 in boot server 410 analyzes client hardwaredetail file 460 in FIG. 4.

Subsequent to the boot server analyzing the data contained in the clienthardware detail file and determining the appropriate operating systemfor the client in step 730, the boot server deploys the operatingsystem, such as, for example, operating system 470 in FIG. 4, to theclient over the network (step 740). It should be noted that steps710-740 may be performed by the boot server simultaneously for aplurality of clients. The process terminates thereafter.

Thus, embodiments of the present invention provide a method, apparatusand computer program product for automatically detecting andinventorying a network boot capable computer and for automaticallydeploying an appropriate operating system to the network boot capablecomputer. The process starts when an initial broadcast packet isreceived from the network boot capable computer. In response toreceiving the initial broadcast packet, a discovery kernel is sent tothe network boot capable computer. The discovery kernel is loaded by thenetwork boot capable computer and generates a hardware details file ofthe network boot capable computer. The hardware details file is receivedfrom the network boot capable computer and is analyzed. After analyzingthe hardware details file using a deployment policy, an appropriateoperating system is selected and deployed to the network boot capablecomputer.

A problem with currently existing systems is that existing systems arelimited to supporting only one type of computer hardware or operatingsystem. Embodiments of the present invention overcome this problem bymaking it possible for at least one central boot server to remotelyidentify, inventory, and manage a plurality of heterogeneous computerplatforms and a plurality of heterogeneous operating systems for aplurality of clients. Also, embodiments of the present invention mayreduce the amount of time a datacenter administrator spends identifying,inventorying, and installing diverse operating systems on a multitude ofheterogeneous computers. Further embodiments of the present inventionusing the identification and inventory of network computers may becompletely automatic reducing human intervention. Still further, theboot server used by the system of an embodiment of the present inventionmay be implemented on a commodity data processing system with standardopen source tools, such as, for example, PXE and DHCP.

It is important to note that while embodiments of the present inventionhave been described in the context of a fully functioning dataprocessing system, those of ordinary skill in the art will appreciatethat the processes of embodiments of the present invention are capableof being distributed in the form of instructions or computer usableprogram code embodied in a computer usable medium and a variety of formsand that embodiments of the present invention applies equally regardlessof the particular type of signal bearing media actually used to carryout the distribution. The computer usable program code comprisesinstructions and/or data. Examples of computer usable media includerecordable-type media, such as a floppy disk, a hard disk drive, a RAM,CD-ROMs, DVD-ROMs, and transmission-type media, such as digital andanalog communications links, wired or wireless communications linksusing transmission forms, such as, for example, radio frequency andlight wave transmissions. The computer usable media may take the form ofcoded formats that are decoded for actual use in a particular dataprocessing system.

The description of embodiments of the present invention have beenpresented for purposes of illustration and description, and are notintended to be exhaustive or limited to the embodiments of the inventionin the form disclosed. Many modifications and variations will beapparent to those of ordinary skill in the art. The embodiments werechosen and described in order to best explain the principles of theinvention, the practical application, and to enable others of ordinaryskill in the art to understand the invention for various embodimentswith various modifications as are suited to the particular usecontemplated.

1. A method in a data processing system central boot server forautomatic detection and inventory of a network boot capable computer andfor automatic deployment of an appropriate operating system to thenetwork boot capable computer, the method comprising: receiving aninitial broadcast packet from the network boot capable computer; sendinga discovery kernel to the network boot capable computer in response toreceiving the initial broadcast packet; receiving a hardware detailsfile generated by the discovery kernel from the network boot capablecomputer; analyzing the hardware details file; and deploying anappropriate operating system from a plurality of operating systemsavailable from the central boot server to the network boot capablecomputer, wherein the appropriate operating system is customizedspecifically for the network boot capable computer by the central bootserver.
 2. The method of claim 1, wherein the network boot capablecomputer is a client.
 3. The method of claim 1, wherein the initialbroadcast packet includes basic system hardware information regardingthe network boot capable computer, and wherein the appropriate discoverykernel sent to the network boot capable computer is based on the basicsystem hardware information, and wherein the basic system hardwareinformation includes one of a manufacturer name or a platform type, andwherein the discovery kernel is an appropriate discovery kernel that isspecific to system hardware for the boot capable computer.
 4. The methodof claim 1, wherein the hardware details file comprises at least one ofa serial number, a manufacturer name, a platform type, a media accesscontrol address, a global unique identifier, a central processing unittype and speed, a network interface card name, and a hard disk type. 5.The method of claim 1, wherein the analyzing step comprises: determiningthe appropriate operating system for the network boot capable computerusing a predetermined deployment policy.
 6. The method of claim 1,further comprising: storing the hardware details file from the networkboot capable computer in a database.
 7. The method of claim 1, whereinthe receiving, sending and deploying steps are performed in at least oneof a preboot execution environment and a dynamic host configurationprotocol/bootstrap protocol.
 8. The method of claim 1, wherein thereceiving, sending, analyzing, and deploying steps are performed by thecentral boot server for a plurality of network boot capable computerssimultaneously.
 9. The method of claim 1, wherein the deploying step isperformed using at least one of a serial number, a manufacturer name, aplatform type, a media access control address, a global uniqueidentifier, a central processing unit type and speed, a networkinterface card name, and a hard disk type.
 10. A central boot servercomprising: a bus system; a memory connected to the bus system, whereinthe memory includes a set of instructions; and a processing unitconnected to the bus system, wherein the processing unit executes theset of instructions to receive an initial broadcast packet from anetwork boot capable computer, send a discovery kernel to the networkboot capable computer in response to receiving the initial broadcastpacket, receive a hardware details file generated by the discoverykernel from the network boot capable computer, analyze the hardwaredetails file, and deploy an appropriate operating system from aplurality of operating systems available from the central boot server tothe network boot capable computer, wherein the appropriate operatingsystem is customized specifically for the network boot capable computerby the central boot server.
 11. The central boot server of claim 10,wherein the network boot capable computer is a client.
 12. The centralboot server of claim 10, wherein the initial broadcast packet includesbasic system hardware information regarding the network boot capablecomputer, and wherein the appropriate discovery kernel sent to thenetwork boot capable computer is based on the basic system hardwareinformation, and wherein the basic system hardware information includesone of a manufacturer name or a platform type, and wherein the discoverykernel is an appropriate discovery kernel that is specific to systemhardware for the boot capable computer.
 13. The central boot server ofclaim 10, further comprising: a database for storing the hardwaredetails file from the network boot capable computer.
 14. The centralboot server of claim 10, wherein the set of instructions to receive,send, analyze, and deploy are executed by the central boot server for aplurality of network boot capable computers simultaneously.
 15. Acomputer program product for automatic detection and inventory of anetwork boot capable computer and for automatic deployment of anappropriate operating system to the network boot capable computer by acentral boot server, the computer program product comprising: acomputer-usable recordable medium having computer usable program codeembodied therein, the computer-usable recordable medium comprising:computer usable program code configured to receive an initial broadcastpacket from the network boot capable computer; computer usable programcode configured to send a discovery kernel to the network boot capablecomputer in response to receiving the initial broadcast packet; computerusable program code configured to receive a hardware details filegenerated by the discovery kernel from the network boot capablecomputer; computer usable program code configured to analyze thehardware details file; and computer usable program code configured todeploy an appropriate operating system from a plurality of operatingsystems available from the central boot server to the network bootcapable computer, wherein the appropriate operating system is customizedspecifically for the network boot capable computer by the central bootserver.
 16. The computer program product as recited in claim 15, whereinthe hardware details file comprises at least one of a serial number, amanufacturer name, a platform type, a media access control address, aglobal unique identifier, a central processing unit type and speed, anetwork interface card name, and a hard disk type.
 17. The computerprogram product as recited in claim 15, further comprising: computerusable program code configured to determine the appropriate operatingsystem for the network boot capable computer using a predetermineddeployment policy.
 18. The computer program product as recited in claim15, further comprising: computer usable program code configured to storethe hardware details file from the network boot capable computer in adatabase.
 19. The computer program product as recited in claim 15,wherein the computer usable program code is configured to receive aninitial broadcast packet from the network boot capable computer, send adiscovery kernel to the network boot capable computer in response toreceiving the initial broadcast packet, and deploy an appropriateoperating system to the network boot capable computer in at least one ofa preboot execution environment and a dynamic host configurationprotocol/bootstrap protocol.
 20. The computer program product as recitedin claim 15, wherein the computer usable program code is configured todeploy an appropriate operating system to the network boot capablecomputer using at least one of a serial number, a manufacturer name, aplatform type, a media access control address, a global uniqueidentifier, a central processing unit type and speed, a networkinterface card name, and a hard disk type.